Important: These forums are for discussions between SkyDemon users. They are not routinely monitored by SkyDemon staff so any urgent issues should be sent directly to our Customer Support.

Mode S Returns From PilotAware


Author
Message
brinzlee
brinzlee
Too Much Forum (4.2K reputation)Too Much Forum (4.2K reputation)Too Much Forum (4.2K reputation)Too Much Forum (4.2K reputation)Too Much Forum (4.2K reputation)Too Much Forum (4.2K reputation)Too Much Forum (4.2K reputation)Too Much Forum (4.2K reputation)Too Much Forum (4.2K reputation)
Group: Forum Members
Posts: 31, Visits: 108
As the PilotAware project has resurfaced and lots of units are in circulation now, would it be possible to address at some point the way Mode S returns are portrayed on SkyDemon by way of a suggestion rather than bearingless targets appear as a cluttered mess over my aircraft, a table in one of the corners with all direct traffic appearing in a series of colours according to signal level received. Rather like the way EasyVFR do it.......I don't like their software but I do like the way traffic is represented.
Thanks
Replies
Tim Dawson
Tim Dawson
SkyDemon Team (678K reputation)SkyDemon Team (678K reputation)SkyDemon Team (678K reputation)SkyDemon Team (678K reputation)SkyDemon Team (678K reputation)SkyDemon Team (678K reputation)SkyDemon Team (678K reputation)SkyDemon Team (678K reputation)SkyDemon Team (678K reputation)
Group: Forum Members
Posts: 8.1K, Visits: 9.4K
Thanks, Lee. I can confirm that when SkyDemon saw the ! that I specified be used as a delimited for our protocol extension to feed callsigns through, it reset the "threat level" to unspecified because that ! also triggers our own internal collision detection code. Since that code doesn't run for bearingless targets, I have modified the Flarm parser to not reset the "threat level" you pass when it's a bearingless target. Incidentally, now that you are (presumably) running your own on-device collision detection code (to power your audible alerts) do you also send Flarm protocol alerts through too, and a meaningful "threat level" for positioned targets?

I have also modified the text rendering so it's the same size, and uses the same black-on-yellow glow, as the positioned targets. The position of the text remains unchanged, which is to draw it on the outside of the "circle of probability" in the direction that you are currently travelling.

Paul, we would consider adding a white background behind the traffic details if enough people asked, but my feeling is that it would obscure much more of the map if we did that. When it comes to rendering other traffic we are very mindful of what things will be like when everybody is broadcasting their location (what we ultimately want). I think to have such a solid background, when we get to that wonderful stage, would not be ideal.
Edited 8/5/2016 11:25:31 AM by Tim Dawson
Paul_Sengupta
P
Too Much Forum (2.8K reputation)Too Much Forum (2.8K reputation)Too Much Forum (2.8K reputation)Too Much Forum (2.8K reputation)Too Much Forum (2.8K reputation)Too Much Forum (2.8K reputation)Too Much Forum (2.8K reputation)Too Much Forum (2.8K reputation)Too Much Forum (2.8K reputation)
Group: Forum Members
Posts: 28, Visits: 181
Tim Dawson - 8/5/2016 11:24:18 AM
Paul, we would consider adding a white background behind the traffic details if enough people asked, but my feeling is that it would obscure much more of the map if we did that. When it comes to rendering other traffic we are very mindful of what things will be like when everybody is broadcasting their location (what we ultimately want). I think to have such a solid background, when we get to that wonderful stage, would not be ideal.

A lot of people have asked, just on the PilotAware forum rather than here! :-) Not specifically for the white box but for some way of increasing the contrast, but others (in real life, not on a forum) have responded favourably when I've suggested the white box idea.

But it could be an option, in the same way as it's an option for the size and colour of your own aeroplane. I, along with many others, find the black on yellow is almost impossible to read at a glance without more detailed study of it, when you have any reasonable background map displayed. It's especially difficult if one's wearing sunglasses!
Peter Robertson
Peter Robertson
Too Much Forum (1.7K reputation)Too Much Forum (1.7K reputation)Too Much Forum (1.7K reputation)Too Much Forum (1.7K reputation)Too Much Forum (1.7K reputation)Too Much Forum (1.7K reputation)Too Much Forum (1.7K reputation)Too Much Forum (1.7K reputation)Too Much Forum (1.7K reputation)
Group: Forum Members
Posts: 48, Visits: 140
Tim Dawson - 8/5/2016 11:24:18 AM
Thanks, Lee. I can confirm that when SkyDemon saw the ! that I specified be used as a delimited for our protocol extension to feed callsigns through, it reset the "threat level" to unspecified because that ! also triggers our own internal collision detection code. Since that code doesn't run for bearingless targets, I have modified the Flarm parser to not reset the "threat level" you pass when it's a bearingless target. Incidentally, now that you are (presumably) running your own on-device collision detection code (to power your audible alerts) do you also send Flarm protocol alerts through too, and a meaningful "threat level" for positioned targets?

I have also modified the text rendering so it's the same size, and uses the same black-on-yellow glow, as the positioned targets. The position of the text remains unchanged, which is to draw it on the outside of the "circle of probability" in the direction that you are currently travelling.

Paul, we would consider adding a white background behind the traffic details if enough people asked, but my feeling is that it would obscure much more of the map if we did that. When it comes to rendering other traffic we are very mindful of what things will be like when everybody is broadcasting their location (what we ultimately want). I think to have such a solid background, when we get to that wonderful stage, would not be ideal.

Hi Tim,

Great to hear you have (as anticipated) identified the problem with depiction of Lee's data. Hopefully Lee will now be able to give us the colour changing rings plus relative altitude and callsign/Tail Reg.

I note your concerns about adding the white background as suggested by Paul. I must admit I have not had any significant problem reading the yellow on black ADSB/P3i data personally, despite needing glasses to read my tablet in flight, so don't anticipate difficulty with the bearingless targets information either - especially now you have adjusted the text to be the same as the ADSB/P3i and indicated the protocol which dictates where this text will appear on the rings. Probably best to give this a try first, but bear Paul's concerns in mind in case people still have problems after the changes are released. An alternative might be a minor further increase in text size if found necessary later.

Regards and thanks once again

Peter
Edited 8/7/2016 12:21:02 PM by Exfirepro
leemoore1966
leemoore1966
Too Much Forum (2K reputation)Too Much Forum (2K reputation)Too Much Forum (2K reputation)Too Much Forum (2K reputation)Too Much Forum (2K reputation)Too Much Forum (2K reputation)Too Much Forum (2K reputation)Too Much Forum (2K reputation)Too Much Forum (2K reputation)
Group: Forum Members
Posts: 24, Visits: 46
Hi Tim

Sorry for the late reply on this.
Actually I am not doing any collision detection (for reasons I know you are aware)
What we have done is set up entry/exit zones, the purpose is nothing more than
to draw your attention to the nav device, the goal is to avoid screen watching, and
I can say it works really well on test flights I have done with the audio to the headsets.

In fact we have 2 types of audio alert for positioned and non-positioned traffic.
There are a couple of good slides which explain this from a presentation done by
Keith Vinning, I can share these when back in the UK, I think this will give clarity

Thx
Lee
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Threaded View
Threaded View
brinzlee - 6/14/2016 10:44:19 AM
Tim Dawson - 6/14/2016 3:08:11 PM
AerialRob - 6/15/2016 8:51:04 PM
brinzlee - 7/28/2016 4:54:39 PM
Exfirepro - 7/28/2016 8:58:12 PM
Tim Dawson - 7/29/2016 9:12:30 AM
Exfirepro - 7/30/2016 7:21:55 PM
Pete - 7/29/2016 2:54:28 PM
flexwingflier - 7/29/2016 4:25:48 PM
leemoore1966 - 7/29/2016 4:52:16 PM
brinzlee - 7/29/2016 6:00:54 PM
Tim Dawson - 8/1/2016 9:29:47 AM
leemoore1966 - 8/1/2016 10:32:03 AM
Tim Dawson - 8/1/2016 11:01:32 AM
leemoore1966 - 8/1/2016 12:43:57 PM
Tim Dawson - 8/2/2016 11:03:38 AM
Exfirepro - 8/2/2016 5:36:16 PM
leemoore1966 - 8/3/2016 12:22:19 PM
Tim Dawson - 8/3/2016 10:03:47 AM
leemoore1966 - 8/3/2016 12:37:42 PM
Exfirepro - 8/3/2016 1:09:26 PM
Tim Dawson - 8/3/2016 1:19:54 PM
leemoore1966 - 8/3/2016 1:30:48 PM
Tim Dawson - 8/3/2016 4:30:25 PM
leemoore1966 - 8/4/2016 8:04:24 AM
Paul_Sengupta - 8/3/2016 11:58:09 PM
Paul_Sengupta - 8/4/2016 1:40:59 PM
Tim Dawson - 8/5/2016 11:24:18 AM
Paul_Sengupta - 8/7/2016 9:32:19 AM
Exfirepro - 8/7/2016 12:17:39 PM
leemoore1966 - 8/9/2016 3:49:09 PM
brinzlee - 8/5/2016 12:18:02 PM
brinzlee - 8/8/2016 7:36:57 AM
Tim Dawson - 8/10/2016 1:45:17 PM
brinzlee - 8/19/2016 11:10:01 AM

Reading This Topic

Login

Explore
Messages
Mentions
Search